The abi-compliance-checker grabs all the .h files it finds
and tries to compile them all. Even though some are not
appropriate for the architecture being run on. Being careful
with preprocessor protections avoids problems.
Vasil Velichkov [Sun, 22 Mar 2020 20:22:13 +0000 (22:22 +0200)]
[PATCH 7/7] cmake: Remove the ORC from the VOLK public link interface
The ORC is an internal dependency that is used to generate SIMD
implementations of some the kernels and no ORC types or functions are
exposed by the VOLK library so adding it to the public link interface is
unnecessary when linking dynamically.
Currently the ORC is added to the INTERFACE_LINK_LIBRARIES property of
the Volk::volk target in VolkTargets.cmake and you need to have the ORC
development files (liborc-*-dev) installed on your system in order to
successfully link a program or library that uses VOLK.
Gbp-Pq: Name 0007-cmake-Remove-the-ORC-from-the-VOLK-public-link-inter.patch
The abi-compliance-checker grabs all the .h files it finds
and tries to compile them all. Even though some are not
appropriate for the architecture being run on. Being careful
with preprocessor protections avoids problems.
* New upstream bugfix release
reason for high urgency:
- Fix loop bound in AVX rotator (only one fixed in 2.2.0-3)
- Fix out-of-bounds read in AVX2 square dist kernel
- Fix length checks in AVX2 index max kernels
The abi-compliance-checker grabs all the .h files it finds
and tries to compile them all. Even though some are not
appropriate for the architecture being run on. Being careful
with preprocessor protections avoids problems.
The abi-compliance-checker grabs all the .h files it finds
and tries to compile them all. Even though some are not
appropriate for the architecture being run on. Being careful
with preprocessor protections avoids problems.
The abi-compliance-checker grabs all the .h files it finds
and tries to compile them all. Even though some are not
appropriate for the architecture being run on. Being careful
with preprocessor protections avoids problems.
Debian, unlike other GNU Radio deployments, does not cross-compile
packages, but builds natively on a set of build machines, including
both arm and armhf.
The abi-compliance-checker grabs all the .h files it finds
and tries to compile them all. Even though some are not
appropriate for the architecture being run on. Being careful
with preprocessor protections avoids problems.
Debian, unlike other GNU Radio deployments, does not cross-compile
packages, but builds natively on a set of build machines, including
both arm and armhf.
File lists are generated in a CMakeLists.txt file with file(GLOB ...), which varies
with the readdir() order. Sorting the lists should help make reproducible builds.
The abi-compliance-checker grabs all the .h files it finds
and tries to compile them all. Even though some are not
appropriate for the architecture being run on. Being careful
with preprocessor protections avoids problems.
Debian, unlike other GNU Radio deployments, does not cross-compile
packages, but builds natively on a set of build machines, including
both arm and armhf.
Philip Balister [Fri, 27 Apr 2018 10:54:33 +0000 (10:54 +0000)]
Fix 32u_reverse_32u for ARM.
* Order of operands in inline asm reversed.
* Worked for some tune setting since gcc generated rbit lr, lr so
order didn't matter. For other tune settings it generated rbit r3, r2
which would fail QA test.
Signed-off-by: Philip Balister <philip@balister.org>
Gbp-Pq: Name 0009-Fix-32u_reverse_32u-for-ARM.patch
* update to v1.4-9-g297fefd
Added an AVX protokernel for volk_32fc_x2_32f_square_dist_scalar_mult_32f
fixed a buffer over-read and over-write in
volk_32fc_x2_s32f_square_dist_scalar_mult_32f_a_avx
Fix 32u_reverse_32u for ARM
File lists are generated in a CMakeLists.txt file with file(GLOB ...), which varies
with the readdir() order. Sorting the lists should help make reproducible builds.
The abi-compliance-checker grabs all the .h files it finds
and tries to compile them all. Even though some are not
appropriate for the architecture being run on. Being careful
with preprocessor protections avoids problems.
Debian, unlike other GNU Radio deployments, does not cross-compile
packages, but builds natively on a set of build machines, including
both arm and armhf.
when building packages (e.g. for openSUSE Linux)
(random) filesystem order of input files
influences ordering of entries in the output,
thus without the patch, builds (in disposable VMs) would usually differ.
See https://reproducible-builds.org/ for why this matters.
File lists are generated in a CMakeLists.txt file with file(GLOB ...), which varies
with the readdir() order. Sorting the lists should help make reproducible builds.
The abi-compliance-checker grabs all the .h files it finds
and tries to compile them all. Even though some are not
appropriate for the architecture being run on. Being careful
with preprocessor protections avoids problems.
Debian, unlike other GNU Radio deployments, does not cross-compile
packages, but builds natively on a set of build machines, including
both arm and armhf.
projects / volk.git / log